System for providing insightful lifestyle notifications

ABSTRACT

A lifestyle service with data and routines storable in a memory of a wearable electronic device is discussed. The lifestyle service has at least a Sleep data routine and an Activity data routine. The lifestyle service can cooperate with an insight engine. The lifestyle service is aware of different types of information contained in one or more time synchronous applications. The system can compare tracked physical activity data with historical data in set increments in light of the information in the time synchronous applications and then communicate notifications to the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of allowed U.S. patent applicationSer. No. 15/699,853, filed Sep. 8, 2017, titled “SYSTEM FOR PROVIDINGINSIGHTFUL LIFESTYLE NOTIFICATIONS”, which is a continuation of U.S.patent application Ser. No. 14/961,668, filed Dec. 7, 2015 (now U.S.Pat. No. 9,782,126, issued Oct. 10, 2017), titled “SYSTEM FOR PROVIDINGINSIGHTFUL LIFESTYLE NOTIFICATIONS”, all of which the full disclosure ofthese applications are incorporated herein by references for allpurposes.

FIELD

The design generally relates to wearable electronics devices formonitoring human lifestyle and providing lifestyle notification.

BACKGROUND

Typically, a wearable electronic device is used as a passive device suchas a watch to provide the time, and they do not interact with thelifestyle of the person wearing the device.

SUMMARY

In general, a health service is discussed. The lifestyle service hasdata and routines storable in a memory in a wearable electronic devicein an executable format. A processor in the wearable electronic devicecan execute the routines of the lifestyle service. The lifestyle serviceincludes at least two routines i) a Sleep data routine and ii) anActivity data routine. The lifestyle service can also cooperate with aninsight engine. The Activity data routine can collect and track data onthe physical activity of a user of the wearable electronic device. TheActivity data routine can cooperate with any of an accelerometer, amagnetometer, a gyroscope, a barometer, a heart rate sensor, and a lightsensor, in the wearable electronic device, to collect this data. TheActivity data routine can store the tracked physical activity data inthe memory of the wearable electronic device. The Activity data routinecan cooperate with a graphic user interface to display the trackedphysical activity data on a display screen of the wearable electronicdevice. A Sleep data routine can collect and track sleep data. Aninsight engine can monitor the tracked sleep data from the Sleep dataroutine and the tracked physical activity data from the Activity dataroutine. The Activity data routine can also compare average trackedphysical activity data with the tracked physical activity data in setincrements that occur at least once per hour.

The insight engine can also monitor one or more time synchronousapplications. The insight engine is configured to monitor, by pullinginformation from or receiving information from, the one or more timesynchronous applications. The time synchronous applications include anyapplication that is configured to keep a time synchronized organizationof at least two of i) personal communication information, ii) past andfuture event information, and iii) fact-based information, each of whichare logged or scheduled in the one or more time synchronousapplications. The applications can be resident either on the wearableelectronic device or on a mobile computing device, such as a smart phonesuch that the mobile computing device can cooperate and communicate withthe wearable electronic device.

The insight engine can make correlations based on at least two of 1) themonitored tracked sleep data from the Sleep data routine, 2) themonitored tracked physical data from the Activity data routine, and 3)any of the monitored personal communication, the monitored past andfuture event information, or the monitored fact-based information loggedor scheduled in the one or more time synchronous applications. Theinsight engine is configured to generate notifications with suggestionsregarding any of i) sleep activity and ii) physical activity to the userof the wearable electronic device based on the correlations.

The insight engine can also make correlations based on the monitoredtracked data from the Sleep data routine and the Activity data routinewith events logged or scheduled in the one or more time synchronousapplication. The insight engine can generate notifications withsuggestions regarding the sleep and physical activity to the user of thewearable electronic device based on at least events logged or scheduledin the one or more time synchronous applications.

The Activity data routine can either directly or by cooperation with theinsight engine, communicate notifications to the user of the wearableelectronic device. The notifications can be communicated by cooperationwith any of i) a speaker in the wearable electronic device to emit anaudible notification, ii) a vibrator in the wearable electronic deviceto communicate a vibration notification, iii) a display screen todisplay information on the display screen to communicate a visualnotification, and iv) any combination of these to the user of thewearable device. The insight engine can then generate the notificationswith suggestions regarding the sleep and physical activity to the user.

In an embodiment, a method of executing a lifestyle service isdiscussed. The method of executing a lifestyle service includes healthservice functionality on a wearable electronic device and has a numberof example steps. The data and routines associated with the lifestyleservice can be stored in a memory of the wearable electronic device. Thelifestyle service, includes at least i) a Sleep data routine and ii) anActivity data routine, that can be executed by a processor of thewearable electronic device. The lifestyle service can be configured tocooperate with an insight engine. Data can be collected and tracked on aphysical activity of the user of the wearable electronic device by theActivity data routine. The Activity data routine can collect data viacooperation with any of an accelerometer, a magnetometer, a gyroscope, abarometer, a heart rate monitor and a light sensor, in the wearableelectronic device. The tracked physical activity data can be stored inthe memory of the wearable electronic device. The tracked physicalactivity data can be displayed on a display screen of the wearableelectronic device. The average tracked physical activity data can becompared with the tracked physical activity data in set increments thatoccur at least once per hour. Notifications can be communicated, eitherdirectly or by cooperation with the insight engine, to the user of thewearable electronic device. Notifications can be communicated bycooperation with any of i) a speaker in the wearable electronic deviceto emit an audible notification, ii) a vibrator in the wearableelectronic device to communicate a vibration notification, iii) adisplay screen to display information on the display screen tocommunicate a visual notification, and iv) any combination of these tothe user of the wearable device.

The insight engine can monitor the time synchronous applications. Thetime synchronous applications include any application that is configuredto keep a time synchronized organization of at least two of i) personalcommunication information, ii) past and future event information, andiii) fact-based information, each of which are logged or scheduled inthe one or more time synchronous applications. The applications caninclude but are not limited to a timeline application and a calendarapplication. The applications can reside either on the wearableelectronic device, a server or on a mobile computing device, such as asmart phone, that can cooperate and communicate with the wearableelectronic device.

The insight engine can monitor the tracked data from the Sleep dataroutine and the Activity data routine. The monitored tracked data fromthe Sleep data routine and the Activity data routine as well as eventslogged or scheduled in the one or more time synchronous applications canbe correlated by the insight engine. Notifications can be generated bythe insight engine with suggestions regarding sleep and physicalactivity to the user of the wearable electronic device. The notificationand suggestion can be based on at least the events, includinginformation, logged or scheduled in the time synchronous applications.The insight engine can monitor the tracked data of the Sleep dataroutine, the tracked data of the Activity data routine, and anyhistorical tracked data for any of these routines. The insight enginecan then compare the data to the events logged or scheduled in the timesynchronous applications in order to generate the notifications withsuggestions regarding the sleep and physical activity to the user.

The insight engine can also make correlations based on at least twoof 1) the monitored tracked sleep data from the Sleep data routine, 2)the monitored tracked physical data from the Activity data routine, and3) any of the monitored personal communication, the monitored past andfuture event information, or the monitored fact-based information loggedor scheduled in the one or more time synchronous applications. Theinsight engine is configured to generate notifications with suggestionsregarding any of i) sleep activity and ii) physical activity to the userof the wearable electronic device based on the correlations.

BRIEF DESCRIPTION OF THE DRAWINGS

The multiple drawings refer to the example embodiments of the design.

FIG. 1A illustrates a block diagram of an example wearable electronicdevice.

FIG. 1B illustrates wearable electronic devices showing examples ofhuman sleep information.

FIG. 2 illustrates wearable electronic devices showing examples of humanactivity information.

FIG. 3 illustrates wearable electronic devices showing examples of humanactivity information.

FIG. 4 illustrates wearable electronic devices showing examples of humansleep information.

FIG. 5 illustrates wearable electronic devices showing examples ofactivity information.

FIG. 6 illustrates wearable electronic devices showing examples of sleepinformation.

FIG. 7 illustrates a block diagram of an embodiment of remote accessand/or communication by a wearable electronic device to other devices ona network.

FIG. 8 illustrates a block diagram of an example computing system thatmay be part of an embodiment of one or more of the wearable electronicdevices discussed herein.

FIG. 9 illustrates wearable electronic devices showing examples of sleepand activity information.

FIG. 10 illustrates wearable electronic devices showing notificationsdisplayed for the wearer.

FIG. 11 illustrates a flow graph of an example method to execute alifestyle service on a wearable electronic device.

While the design is subject to various modifications and alternativeforms, specific embodiments thereof have been shown by way of example inthe drawings and will herein be described in detail. The design shouldbe understood to not be limited to the particular forms disclosed, buton the contrary, the intention is to cover all modifications,equivalents, and alternatives falling within the spirit and scope of thedesign.

DETAILED DISCUSSION

In the following description, numerous specific details are set forth,such as examples of wearable electronic devices, named components,connections, number of databases, etc., in order to provide a thoroughunderstanding of the present design. It will be apparent; however, toone skilled in the art that the present design may be practiced withoutthese specific details. In other instances, well known components ormethods have not been described in detail but rather in a block diagramin order to avoid unnecessarily obscuring the present design. Thus, thespecific details set forth are merely exemplary. The specific detailsdiscussed in one embodiment may be reasonably implemented in anotherembodiment. The specific details may be varied from and still becontemplated to be within the spirit and scope of the present design.

In general, a lifestyle service that includes but is not limited tohealth service functionality with data and routines is discussed. Thelifestyle service can include various routines including i) a Sleep dataroutine, ii) an Activity data routine, and iii) a State of Mind routine.The lifestyle service can also cooperate with an insight engine.

The Activity data routine can collect and track data on a physicalactivity of the user of the wearable electronic device. The Activitydata routine can collect data by cooperation with sensors, which includeany of an accelerometer, a magnetometer, a gyroscope, and a lightsensor, in the wearable electronic device. The Activity data routine canthen store the tracked physical activity data in the memory of thewearable electronic device. The Activity data routine can also cooperatewith a graphic user interface to display the tracked physical activitydata on a display screen of the wearable electronic device.

Likewise, the Sleep data routine can collect and track data on a sleeppattern of the user of the wearable electronic device. The Sleep dataroutine can cooperate with any of the accelerometer, the magnetometer,the gyroscope, and the light sensor, in the wearable electronic deviceto collect data. The Sleep data routine can store the tracked sleep datain the memory of the wearable electronic device. The Sleep data routinecan cooperate with the graphic user interface to display the trackedsleep pattern data on the display screen of the wearable electronicdevice.

The insight engine can any of i) compare a current average trackedphysical activity data or tracked sleep data to a historical average ofthe tracked data in a set increment of time, such as at least once perhour, and/or ii) compare a total amount of current tracked physicalactivity data to a historical total amount of tracked physical activitydata in the set increment of time. The Activity data routine can eitherdirectly or by cooperation with the insight engine, communicatenotifications to the user of the wearable electronic device. Thenotifications to the user of the wearable device can be sent bycooperation with any of i) a speaker in the wearable electronic deviceto emit an audible notification, ii) a vibrator in the wearableelectronic device to communicate a vibration notification, iii) adisplay screen to display information on the display screen tocommunicate a visual notification, and iv) any combination of these.

The insight engine is configured to provide suggestions includingguidance, coaching, suggested actions, feedback, etc. The insight enginecan also generate notifications with suggestions regarding sleepactivity, physical activity, and mood or state of mind for the user ofthe wearable electronic device. The lifestyle service is aware ofinformation contained in one or more time synchronous applications. Thelifestyle service and insight engine cooperate to compare trackedphysical activity data with historical data in set increments in lightof the information in the time synchronous applications and thencommunicate insightful notifications to the user.

FIG. 1A illustrates a block diagram of an example human wearable device.The block diagram 100 shows a human wearable device 175 that cancommunicate with a mobile device such as a smart phone 180. The humanwearable device includes one or more processors 176, memories 174, andports 172. The lifestyle service 160 that includes at least includesActivity data routine 164 and Sleep data routine 163 can execute on theprocessors 176. The human wearable device also includes a communicationmodule 156 that can run on the processors and for communicating tooutside of the human wearable devices.

As described, in an embodiment, a wearable electronic device 175 caninclude one or more processors 176. The processors can execute thelifestyle service 160 that at least includes Activity data routine 164and Sleep data routine 163. The wearable electronic device 175 caninclude a communication module 156 such that the lifestyle service 160can communicate through the communication module with a mobile device180 through ports 172. In addition, the lifestyle service routines canbe stored in the memories 174 of wearable electronic device 175. Thecommunication module 156 can transmit wirelessly through a network toanother computing device such as a mobile device 180 cooperating withthe wearable electronic device. (See, for example, FIGS. 7-8). In anexample, the wearable electronic device 175 and the mobile device 180can directly communicate using Bluetooth. In other embodiments, thecommunication may occur thru Zigbee, Wi-Fi, cellular network, or other.

In an embodiment, the lifestyle service 160 with data and routines canbe stored in executable format in a memory 174 in a wearable electronicdevice 175. A processor 176 in the wearable electronic device 175 canexecute the routines of the lifestyle service. The lifestyle service caninclude at least two routines i) a Sleep data routine 163 and ii) anActivity data routine 164. Also, the lifestyle service can cooperate 160with an insight engine 158. In an example, the insight engine 158 is inthe mobile device 180. The insight engine 158 can i) execute on a webserver and communicate through a mobile computing device, such as asmart phone, with the wearable electronic device, ii) execute on themobile computing device and communicate with the wearable electronicdevice, iii) execute on the processors of the wearable electronicdevice, or iv) execute on any combination of the three implementationsabove.

In an embodiment, the insight engine 158 can monitor one or more timesynchronous applications. The insight engine 158 can monitor, by pullinginformation from or receiving information from, one or more timesynchronous applications. The time synchronous applications include anyapplication that is configured to keep a time synchronized organizationof at least two of i) personal communication information, ii) past andfuture event information, and iii) fact-based information, each of whichare logged or scheduled in the one or more time synchronousapplications. For example, time synchronous applications include but arenot limited to a timeline application and a calendar application. Thesynchronous applications can reside either on the wearable electronicdevice or on a mobile computing device that can cooperate andcommunicate with the wearable electronic device. The timelineapplication can have such events or information logged in a time formatsuch as personal communication information, past and future eventinformation and fact-based information. Personal communication caninclude emails, tweets, text messages, Facebook notifications, and more.Event information can include calendar events or reminders. Fact basedinformation can include sport scores, weather information, etc.

Some example types of information scheduled or logged into the timesynchronous applications can include at 4 AM a weather event of rain, at5:10 AM sunrise, at 5:15 AM wake-up alarm, at 6:10 AM a missed telephonecall, a calendar event for a lunch meeting from 11:30 to 1 PM, abusiness meeting from 3 PM to 4 PM, a workout at the gym from 7 to 8 PM.Each one of these time ordered information elements may come from thesame or different sources, yet are arranged and placed in a useful timesynchronized manner for the user.

The insight engine can also monitor tracked data from the Sleep dataroutine such as sleep pattern data and sleep activity data. The insightengine can then monitor the tracked data from the Sleep data routine,the tracked data from Activity data routine, any tracked data from aState of Mind routine, and any historical tracked data for any of theseroutines. The insight engine can make correlations based on themonitored tracked data from the Sleep data routine, the Activity dataroutine, and State of Mind routine, with events or information logged orscheduled in the one or more time synchronous application. Thecorrelation may include evaluating and then making a nexus or conclusionfrom the evaluation. The insight engine is configured to makecorrelations based on at least two of 1) the monitored tracked sleepdata from the Sleep data routine, 2) the monitored tracked physical datafrom the Activity data routine, and 3) any of the monitored personalcommunication, the monitored past and future event information, or themonitored fact-based information logged or scheduled in the one or moretime synchronous applications. The insight engine can generatenotifications with suggestions regarding any of i) sleep activity andii) physical activity to the user of the wearable electronic devicebased on the correlations. The insight engine can also generatenotifications with suggestions regarding the sleep and physical activityto the user of the wearable electronic device based on at leastinformation events logged or scheduled in the one or more timesynchronous applications. The insight engine can monitor the trackeddata of the Sleep data routine, the tracked data of the Activity dataroutine, and any historical tracked data for any of these routines andthen compare the data to the events logged or scheduled in the one ormore time synchronous applications. The insight engine can then generatethe notifications with suggestions regarding the sleep and physicalactivity to the user.

Additionally, the insight engine 158 can 1) execute on a web server 204Aand communicate through the mobile computing device 180 with thewearable electronic device, 2) execute on the mobile computing device180 and communicate with the wearable electronic device, 3) execute onthe processor of the wearable electronic device as shown in FIG. 1A, 4)execute on any combination of the three implementations above. In anexample, the insight engine 158 is resident in the mobile device 180.

Additionally, a wearable electronic device can have one or more memories174 and one or more processors 176. The wearable electronic device canalso have one or more of 162: an accelerometer, a magnetometer, agyroscope, a barometer, a heart rate sensor, and a light sensor. Thewearable electronic device can further include a graphic user interfaceand a display screen, one or more of a speaker and a vibrator, acommunication module that can execute on the processors 176, an insightengine 158, and a lifestyle service 160. The wearable electronic devicecan have its own global positioning system chip and GPS app or merelyhave a routine configured to pull information from a GPS app on acooperating mobile device.

FIGS. 1B and 6 illustrate human wearable electronic devices showingexamples of sleep information.

In an embodiment, the Sleep data routine can collect and track data on asleep pattern of the user of the wearable electronic device 175. TheSleep data routine can collect data via cooperation with any of theaccelerometer, the magnetometer, the gyroscope, and the light sensor, inthe wearable electronic device, and can store the tracked sleep patterndata in the memory of the wearable electronic device. The Sleep dataroutine can cooperate with the graphic user interface to display thetracked sleep pattern data and/or tracked sleep activity data on thedisplay screen of the wearable electronic device. For example, the userinterface presents a bar around the displayed numerical data and the barhas lighter and darker shades to indicate a difference between deepsleep and regular sleep.

FIGS. 2, 3 and 5 illustrate human wearable devices showing examples ofactivity information. For example, FIG. 3 illustrates the lifestyleservice displaying the tracked physical activity data over a set periodof time on the display. The set period of time can be shorter than a daysuch as an hour increment of time. In the example in FIG. 2, the trackedphysical activity is shown vertically for each day of the week and theline going horizontally across shows the averages for the sameincrements of time for week days as a whole and week-end days as awhole. The lifestyle service may display the tracked physical activitydata over a set period of time on the display so that the user cancompare individual workouts and boost the user's performance on theirnext workout.

In an embodiment, the Activity data routine can collect and track dataon a physical activity of a user of the wearable electronic device. TheActivity data routine 164 can collect data via cooperation with any ofan accelerometer, a magnetometer, a gyroscope, and a light sensor, inthe wearable electronic device. The Activity data routine can store thetracked physical activity data in the memory 174 of the wearableelectronic device. The Activity data routine can cooperate with agraphic user interface to display the tracked physical activity data ona display screen of the wearable electronic device. (See, for example,FIGS. 2, 3, 5, and 9.)

In an embodiment, the lifestyle service 160 can store tracked physicalactivity data and tracked sleep pattern data every minute. The lifestyleservice 160 can then calculate average tracked physical activity dataand average tracked sleep pattern data every 15 minutes. This can allowthe lifestyle service to calculate averages at every minute of the day,further allowing the lifestyle service flexibility of both i) whenduring a day to trigger and provide the notification giving feedback ona relative goal of the day and ii) what a content of the suggestionshould be based on either a current tracked physical activity data orcurrent tracked sleep data compared to the relative goal of the day.Thus, how close the user is to achieving the goal is updated every 15minutes.

In an embodiment, at least once per hour, an algorithm in the lifestyleservice 160 is configured to track and then store one or more kinds ofphysical activities engaged in by the user, such as a number of stepstaken. The algorithm can then also translate based on the user's heightthe number of steps taken into an amount of calories burned and distancetraveled. The algorithm can also track the user's active time based onthe type of changes detected in the user's movement as detected by thevarious sensors. The algorithm can also track other forms of user'sexercise by configuring a number of scheduled physical activity periodsand rest periods so that the user can compare individual workouts andboosts the user's performance on their next workout.

Thus, the lifestyle service can cooperate with the graphic userinterface to display steps taken and calories burned by the userthroughout a day. The lifestyle service can also display user's currentstep counts and progress towards user's daily goal. The user can get avibration when the user reaches daily average. In other embodiments, theuser may get a vibration on reaching individually set goals or for otherachievements. The lifestyle service cooperating with the graphic userinterface can display graphs of individual workouts on daily, weekly, ormonthly basis and to display tracked physical activity including dailyprogress and summary data for a user selectable amount of days.

FIGS. 4 and 9 illustrate human wearable devices showing examples of bothphysical activity and sleep information.

FIG. 4 illustrates human wearable electronic devices showing examples ofsleep information display as current activity in vertical bar graphs andaverages for weekdays and weekend days indicated by a horizontal lineacross the graph. The Sleep data routine is configured to collect andtrack data on the sleep data of the user of the wearable electronicdevice, via cooperation with sensors 887, which include any of theaccelerometer, the magnetometer, the gyroscope, the barometer, the heartrate sensor, and the light sensor, in the wearable electronic device.The Sleep data routine may store the tracked sleep data in the memory ofthe wearable electronic device. The Sleep data routine may cooperatewith the graphic user interface to display the tracked sleep data on thedisplay screen of the wearable electronic device. The Sleep data routineand/or the insight engine may be configured to any of i) track a currentaverage tracked sleep data in a set increment of time and ii) compare acurrent total amount of sleep data in the set increment of time to anyhistorical tracked data for the same increment of time. The setincrement of time may be, for example, less than a twenty-four hourperiod of time, which is shown on the display screen. The Sleep dataroutine is configured to either directly or by cooperation with theinsight engine, communicate the notifications regarding sleep to theuser of the wearable electronic device by cooperation with any of i) thespeaker in the wearable electronic device to emit an audiblenotification, ii) the vibrator in the wearable electronic device tocommunicate a vibration notification, iii) the display screen to displayinformation on the display screen to communicate a visual notification,and iv) any combination of these to the user of the wearable device.

Next, in an example, the lifestyle service can both log and trackspecific activities such as sleep data that occur in the fixedincrements of less than an hour. The lifestyle service then may comparethe current logged activity to previous tracked activity for the sameperiod of tracked time. For example, in FIG. 6 the lifestyle servicecooperates with the display to show the user had 3.0 hours of deep sleeplast night while the user's historical average is 3.4 hours of deepsleep for that same increment of time. Both the Sleep data routine andthe Activity data routine can track the data in set increments thatoccur at least once per hour, such as every minute of the day. Both theSleep data routine and the Activity data routine then store this data inthe memory of the wearable electronic device. The locally stored data inthe memory of the wearable electronic device may be then periodicallysent to a server and database of the insight engine to store this dataas historical data on the user.

In an embodiment, the insight engine 160 can monitor all four of theSleep data routine, the Activity data routine, the State of Mindroutine, and any set goals for any of these routines. The insight engineis then configured to take an action of adding an event corresponding toany of a sleep activity of the user, the physical activity of the user,or a mood of the user back into any of the time synchronous applicationswhen the set goals for the sleep activity, the physical activity, or themood of the user are not yet met.

FIG. 10 illustrates human wearable devices showing notificationsdisplayed for the human wearer. For example, but not limited to anotification may convey to the user that they need to take 500 steps. Anotification may communicate to the user that they, for example, slept 7hours, which is more than the user's historical average for a night. Anotification may convey to the user that they, for example, should takea stretch to achieve their physical activity goal for that hour. Anotification may communicate to the user many other insightfulsuggestions based on the insight engine making correlations. A user maysimply read a notification or may take an action, such as the “zzz”option, embedded in the notifications, which makes the notification popup again at a later point in time.

The insight engine can monitor tracked sleep data from the Sleep dataroutine and tracked physical activity data from the Activity dataroutine. The insight engine can make correlations based on at least twoof 1) the monitored tracked sleep data, including current and historicaltracked data, from the Sleep data routine, 2) the monitored trackedphysical data, including current and historical tracked data, from theActivity data routine, and 3) any of the monitored personalcommunication, the monitored past and future event information, or themonitored fact-based information logged or scheduled in the one or moretime synchronous applications. The insight engine is configured togenerate notifications with suggestions regarding any of i) sleepactivity and ii) physical activity to the user of the wearableelectronic device based on these correlations.

The lifestyle service may be configured to generate some of thenotifications with suggestions regarding sleep and the physical activitybased on a previous day's individual effort. In an embodiment, theinsight engine can compare a current tracked physical activity data tohistorical averages of the tracked data and then cross reference anyevents or information scheduled in the time synchronous applications inorder to decide both 1) whether to generate the notification at thistime and then 2) what to convey in the notification. The insight enginehas one or more routines configured to both 1) decide whether to sendthe notification with the suggestion and 2) what to convey in thenotification based on a comparison of factors of i) remaining physicalactivity still needed to achieve a historical average amount of physicalactivity, ii) what types of events are yet to still occur according toevents currently scheduled in the one or more time synchronousapplications, and iii) a time duration associated with each of thecurrently scheduled events yet to occur in that day. Thus, the insightengine can use historical averages of tracked data to control a triggerof when to send a notification with suggestions regarding sleep,activity, and mood that may require actions by a user.

As an example, if the user has not slept very well, the insight enginecan suggest the user to go to bed earlier and/or set a pin on thetimeline application. In another example, if user's steps are underaverage, the insight engine can look at user's timeline application andsuggest a time for taking a walk. If the user's goal is to sleep acertain amount of hours and the insight engine sees that the user has anevent such as an 8 AM meeting, and then the insight engine can send anotification suggesting the user to go to bed early.

In an embodiment, the insight engine can compare the current trackeddata to historical averages of the tracked data and then correlated thiswith the events logged/scheduled in the time synchronous applications inorder to decide both whether to generate a notification at this time andthen what to convey in the notification.

Thus, the insight engine can evaluate what type of event is logged inthe time synchronous applications in order to decide whether to generatea notification at this time by comparing properties of the event thatmay include duration, timing, category and location.

The insight engine may evaluate tracked data from typically unassociateddata sources of i) sleep activity from the Sleep data routine, ii)physical activity from the Activity data routine, and iii) scheduledevents on any of the time synchronous applications in order to makebeneficial notifications with suggestions regarding the sleep activityand the physical activity to the user of the wearable electronic device.The insight engine may evaluate what type of event is scheduled in thetime synchronous application by comparing properties of the event thatmay include, but are not limited to, duration, timing, category andlocation. The insight engine is configured to decide whether to generatethe notification at this time by comparing the types of scheduled eventsthat have not yet occurred to an amount of either sleep activity orphysical activity the user still needs to achieve a set goal. Thus, theinsight engine may provide an insightful suggestion in the notificationon achieving that set goal rather than an arbitrary posting of the setgoal.

The lifestyle service is configured to i) collect tracked data from theSleep data routine, the Activity data routine, and the State of Mindroutine, ii) push notifications with suggestions from the insightengine, and iii) display current tracked data as well as historicaltracked data.

In another embodiment, lifestyle service is configured to i) collecttracked data from the Sleep data routine, the Activity data routine, andthe State of Mind routine, ii) correlate the collected information withthe event based information, fact based information or personalcommunication information to generate notifications ii) pushnotifications with suggestions from the insight engine, and iii) displaycurrent tracked data as well as historical tracked data.

The Activity data routine can either directly or by cooperation with theinsight engine 158, communicate notifications to the user of thewearable electronic device by cooperation with any of i) a speaker 897in the wearable electronic device to emit an audible notification, ii) avibrator 899 in the wearable electronic device to communicate avibration notification, iii) a display screen 891 to display informationon the display screen to communicate a visual notification, and iv) anycombination of these to the user of the wearable device. In anembodiment, a separate routine neither the activity data routine nor theinsight engine) is configured to work with both of these two todetermine and communicate the notifications.

Likewise, the Sleep data routine can compare average tracked sleeppattern data with the tracked sleep pattern data in set increments thatoccur at least once per day. The Sleep data routine can either directlyor by cooperation with the insight engine, communicate notifications tothe user of the wearable electronic device. The Sleep data routine cansend the notifications through any of i) the speaker in the wearableelectronic device to emit an audible notification, ii) the vibrator inthe wearable electronic device to communicate a vibration notification,iii) the display screen to display information on the display screen tocommunicate a visual notification, and iv) any combination of these tothe user of the wearable device. In an embodiment, a separate routine(not the sleep data routine, or the insight engine) is configured towork with both of these two to determine and communicate thenotifications.

FIG. 11 illustrates a flow graph of an example method to execute alifestyle service on a wearable electronic device. The flow diagram 1100can be used for describing the method and the steps may be performed outof literal order when logically possible. Data and routines of thelifestyle service are stored in the memory of wearable electronicdevice. The health service's Sleep data routine, State of Mind routine,and Activity data routines can be executed (1110) by one or moreprocessors. As an example, the flow diagram 1100 can be executed on thehuman wearable device 100 of FIG. 1A.

The lifestyle service is configured to cooperate with insight engine tocollect and track data on physical activity of a user of the wearableelectronic device (1120). Data collection can be done via cooperationwith any of an accelerometer, a magnetometer, a gyroscope, barometer,heart rate monitor and a light sensor, in the wearable electronicdevice. (See, for example, FIG. 1A.)

The tracked physical activity data is stored in the memory and thetracked physical activity data displayed on a display screen (1130). Asan example, FIGS. 2, 3, 5, and 9 display physical activity data.

Average tracked physical activity data is compared with the tracked datafor at least once per hour and notifications are communicated to theuser (1140). The notification related to physical activity data can besent directly by the lifestyle service 160 or can be sent by thelifestyle service cooperating with the insight engine 158. In anexample, the insight engine can do data analysis and comparison for thelifestyle service and the lifestyle service can send the notification.

Time synchronous applications such as a calendar are monitored, as wellas the tracked data from the State of Mind routine, the Sleep dataroutine, and the Activity data routine are monitored (1150). The timesynchronous applications include any application that is configured tokeep a time synchronized organization of at least two of i) personalcommunication information, ii) past and future event information, andiii) fact-based information, each of which are logged or scheduled inthe one or more time synchronous applications (1150). In an example,these time synchronous applications include but are not limited to atimeline or a calendar, which are monitored by the insight engine. Thetime synchronous applications can reside on the human wearable device oron a mobile device coupled to the human wearable device. Likewise, theinsight engine can reside on the human wearable device or the mobiledevice. In another example, the insight engine and the time synchronousapplications can reside on a webserver and the monitoring can beperformed by the webserver. Then the webserver can communicate throughthe mobile device to the human wearable device. In yet another example,the insight engine and the time synchronous applications can bedistributed between the human wearable device, the mobile device, andthe webserver. The webserver and the mobile device can wirelesslycommunicate and the human wearable device and the webserver canwirelessly communicate via the mobile device. The insight engine maymonitor these one or more time synchronous applications by pullinginformation from or receiving information from the one or more timesynchronous applications (1150).

The monitored tracked data from Sleep data routine, State of Mindroutine, and Activity data routine are correlated with the events loggedin the synchronous applications (1160). The insight engine can correlatethe tracked data and the events. As an example, an event can be ascheduled meeting or an appointment.

Additionally, the insight engine may correlate based on at least twoof 1) the monitored tracked sleep data from the Sleep data routine, 2)the monitored tracked physical data from the Activity data routine, and3) any of the monitored personal communication, the monitored past andfuture event information, or the monitored fact-based information loggedor scheduled in the one or more time synchronous applications (1160).The insight engine may generate notifications (1170) with suggestionsregarding any of i) sleep activity and ii) physical activity to the userof the wearable electronic device based on the correlations (1160).

Notifications with suggestions regarding sleep and physical activity tothe user are generated (1170). The notifications can be generated by theinsight engine. The notifications can suggest actionable items. As anexample, after analyzing the tracked data, the insight engine canrealize the user's physical activity is below daily average and there isno scheduled meeting or appointment on the user's calendar in the nextfew hours. Then, the insight engine may send a notification suggestingthe user to take a walk. In another example, the insight engine mayacquire weather reports from the webserver and suggest taking a walkonly if weather conditions permit.

Next, in general, the wearable electronic device includes one or moresystems and can be coupled to one or more networks. FIGS. 7-8 illustrateadditional example environments to implement the concepts.

In an embodiment, the wearable electronic device is a smart watch whichfeatures a black and white Sharp Memory LCD display screen, aprogrammable CPU, memory, storage, Bluetooth, a vibrating motor, amagnetometer, an ambient light sensor, and an accelerometer. Thesefeatures extend the smart watch's use beyond just displaying the time onthe display screen and into many roles including interacting withsmartphone notifications, activity tracking, gaming, map display, golftracking, and more. The smart watch is compatible with Android and iOSdevices. When connected to one of these devices via Bluetooth, the smartwatch can (but may not need to) pair with that device and vibrate anddisplay text messages, fitness information, emails, incoming calls, andnotifications from social media accounts. The smart watch can also actas a remote control for the phone function in the paired device, or forother paired devices containing a camera such as the GoPro. As anexample, an associated app store can provide a software development kit(SDK) to develop applications and watchfaces associated with the smartwatch.

In another embodiment, the wearable electronic device may be a belt, anecklace, lapel pin or other form of wearable device.

The housing also has a computer readable storage medium in the housingaccessible to the processor for storing instructions executable by theprocessor to generate the number of different operations on the onscreendisplay.

FIG. 8 illustrates a block diagram of an example computing system thatmay be used in an embodiment of one or more of the servers, a wearableelectronic device, and client devices discussed herein. The computingsystem environment 800 is only one example of a suitable computingenvironment, such as a client device, server, wearable electronicdevice, etc., and is not intended to suggest any limitation as to thescope of use or functionality of the design of the computing system 810.Neither should the computing environment 800 be interpreted as havingany dependency or requirement relating to any one or combination ofcomponents illustrated in the exemplary operating environment 800.

In an embodiment, the wearable electronic device is an electronicsmartwatch that comes with a Gorilla Glass 64-color LED e-paper display,with 144×168 pixels and a pixel density of 182 ppi. The wearableelectronic device has a color display, and still retains a backlight aswell. The wearable electronic device also has a vibrating motor forsilent alarms, and smart notifications. The wearable electronic devicecan have a redesigned charging cable that can magnetically attach itselfto the wearable electronic device in order to maintain its waterresistance. The wearable electronic device can also be equipped with anambient light sensor, 6 axis accelerometer, etc. In an example, thewearable electronic device can have axis accelerometer with gesturedetection, a vibrating motor, an ambient light sensor, a compass, a gyrometer, a magnetometer, a pedometer, a microphone, and four physicalbuttons for user input. In alternative embodiments, the display mayinclude a touch screen, a scroll bar, one or more buttons, a rotatingbezel or a combination of any of the elements for user input.

In an example, the display can have 144×168 pixel Sharp Memory LCD“e-paper”, or 144×168 pixel black and white memory LCD using an ultralow-power “transflective LCD” with a backlight, or 1.25 inch 64-colorLED backlit e-paper display.

In an embodiment, the wearable electronic device can connect through awireless network to an app store having many applications and watchfacesthat can be downloaded. The applications include notifications foremails, calls, text messages & social media activity; stock prices;activity tracking (movement, sleep, estimates of calories burned);remote controls for smartphones, cameras & home appliances; turn-by-turndirections (using the GPS receiver in a smartphone or tablet); displayof RSS or JSON feeds; and also include hundreds of custom watch faces.

In an embodiment, the wearable electronic device can originally beshipped with applications pre-installed. These applications can use datareceived from a connected phone for distance, speed, and rangeinformation. The applications can also directly connect to a backendserver on the cloud. More applications are downloadable via a mobilephone or tablet, and an SDK is freely available.

In an embodiment, the wearable electronic device can integrates with anyphone or tablet application that sends out native iOS or Androidnotifications.

In an embodiment, the wearable electronic device's firmware operatingsystem is based on a Free RTOS kernel and uses Newlib, the STM32Peripheral Lib, the Ragel state machine compiler, and a UTF-8 Decoder.As an example, the wearable electronic device includes a 64-colore-paper display with Gorilla Glass, a thinner and more ergonomicchassis, plastic casing and a microphone. In an example, the wearableelectronic device can have a Marine Grade steel chassis encasing withbezel and a PVD matte polishing finish and a tough 2.5D color e-paperdisplay.

In an embodiment, the wearable electronic device is an electronic watchand includes a small accessory port on the back of the watch face. Openhardware platform of the wearable electronic device lets developersdevelop new third-party straps that connects to a special port at theback of the watch and can add additional features like GPS, heart ratemonitors, extended battery life and other things to the watch. Itenables the wearer to attach additional equipment to the watch,including sensors, batteries, etc.

In an embodiment, the Activity data routine 164 can collect and trackdata from two or more different types of physical activities of the userof the wearable electronic device 100. The Sleep data routine 163 canalso collect, store, and track the sleep data which consists of one ormore patterns of sleep of the user, such as stages of sleep includingdeep or regular sleep, as well as one or more sleep activities, such astotal amount of sleep, of the user of the wearable electronic device.

In an embodiment, the lifestyle service can further include a State ofMind routine. The State of Mind routine can be activated by the user,and if activated, the user interface is configured to periodically askthe user questions about a user's mood. The user can be offered a choiceof responding to the mood questions by either inputting a reply or bydeclining to respond. The State of Mind routine can store the moodpattern responses in the memory 174 of the wearable electronic device.The insight engine is configured to both monitor these mood responsesand make correlations based on these mood responses to generatenotifications with suggestions on a mood of the user. The State of Mindroutine can glean the user's state of mind from information in the timesynchronous applications as well as things the routine gleans from howthe user reacts to any suggestions given by the lifestyle service aswell as the user's response to the mood questions.

Thus, the lifestyle service also includes a State of Mind routine andthe insight engine can monitor collected tracked data from the State ofMind routine and correlate the Mood data with the tracked physicalactivity data and tracked sleep pattern data. Then the lifestyle servicecan cross reference this data from the different sources of loggedevents in the time synchronous applications in order to generate anotification with suggestions regarding sleep, physical activity, andmood to the user.

Thus, the lifestyle service can be useful for both if the user intendsto count steps for individual walking or other workouts, as well as ifthe user want to track all-day steps or cumulative physical activityworkouts for the day.

In an embodiment, a web server can host the insight engine with logicfor detecting a specific pattern of behavior for each user over ahistorical period of time greater than 2 days, as well as the webservercan have a list of notifications with suggestions preset in a librarythat can be accessed and additionally populated with the specific datafor that user.

Computing System

With reference to FIG. 8, components of the computing system 810 mayinclude, but are not limited to, a processing unit 820 having one ormore processing cores, a system memory 830, and a system bus 821 thatcouples various system components including the system memory to theprocessing unit 820. The system bus 821 may be any of several types ofbus structures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. By wayof example, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)locale bus, and Peripheral Component Interconnect (PCI) bus.

Computing system 810 typically includes a variety of computingmachine-readable media. Computing machine-readable media can be anyavailable media that can be accessed by computing system 810 andincludes both volatile and nonvolatile media, removable andnon-removable media. By way of example, and not limitation, computingmachine-readable mediums uses include storage of information, such ascomputer readable instructions, data structures, other executablesoftware or other data. Computer storage mediums include, but are notlimited to, RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other tangible medium which can be usedto store the desired information and which can be accessed by computingdevice 800. Transitory media such as wireless channels are not includedin the machine-readable media. Communication media typically embodiescomputer readable instructions, data structures, other executablesoftware, or other transport mechanism and includes any informationdelivery media. As an example, some clients on network 220 of FIG. 7 maynot have any optical or magnetic storage.

The system memory 830 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 831and random access memory (RAM) 832. A basic input/output system 833(BIOS), containing the basic routines that help to transfer informationbetween elements within computing system 810, such as during start-up,is typically stored in ROM 831. RAM 832 typically contains data and/orsoftware that are immediately accessible to and/or presently beingoperated on by processing unit 820. By way of example, and notlimitation, FIG. 8 illustrates that RAM can include a portion of theoperating system 834, other executable software 836, and program data837.

The computing system 810 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 8 illustrates a solid-state memory 841. Otherremovable/non-removable, volatile/nonvolatile computer storage mediathat can be used in the exemplary operating environment include, but arenot limited to, USB drives and devices, flash memory cards, solid stateRAM, solid state ROM, and the like. The solid-state memory 841 istypically connected to the system bus 821 through a non-removable memoryinterface such as interface 840, and USB drive 851 is typicallyconnected to the system bus 821 by a removable memory interface, such asinterface 850.

As an example, the computer readable storage medium 841 stores OperatingSystem software for smart watches to cooperate with both Android OS andiOS.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 8, provide storage of computer readableinstructions, data structures, other executable software and other datafor the computing system 810. In FIG. 8, for example, the solid statememory 841 is illustrated for storing operating system 844, otherexecutable software 846, and program data 847. Note that thesecomponents can either be the same as or different from operating system834, other executable software 836, and program data 837. Operatingsystem 844, other executable software 846, and program data 847 aregiven different numbers here to illustrate that, at a minimum, they aredifferent copies. In an example, the operating system, Pebble OS, can bea customized Free RTOS kernel that can communicate with Android and iOSapps using Bluetooth, Wi-Fi, cellular or other communicationmethodology.

A user may enter commands and information into the computing system 810through input devices such as a keyboard, touchscreen, or even pushbutton input component 862, a microphone 863, a pointing device and/orscrolling input component 861, such as a mouse, trackball or touch pad.The microphone 863 may cooperate with speech recognition software. Theseand other input devices are often connected to the processing unit 820through a user input interface 860 that is coupled to the system bus,but may be connected by other interface and bus structures, such as aparallel port, game port or a universal serial bus (USB). A displaymonitor 891 or other type of display screen device is also connected tothe system bus 821 via an interface, such as a display and videointerface 890. In addition to the monitor, computing devices may alsoinclude other peripheral output devices such as speakers 897, a vibrator899, and other output device, which may be connected through an outputperipheral interface 890.

The computing system 810 may operate in a networked environment usinglogical connections to one or more remote computers/client devices, suchas a remote computing device 880. The remote computing device 880 may bea wearable electronic device, a personal computer, a hand-held device, aserver, a router, a network PC, a peer device or other common networknode, and typically includes many or all of the elements described aboverelative to the computing system 810. The logical connections depictedin FIG. 8 include a local area network (LAN) 871 and a wide area network(WAN) 873, but may also include other networks. Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets and the Internet. A browser application may beresident on the computing device and stored in the memory.

When used in a LAN networking environment, the computing system 810 isconnected to the LAN 871 through a network interface or adapter 870,which can be a Bluetooth or Wi-Fi adapter. When used in a WAN networkingenvironment, the computing system 810 typically includes a modem 872,e.g., a wireless network, or other means for establishing communicationsover the WAN 873, such as the Internet. The wireless modem 872, whichmay be internal or external, may be connected to the system bus 821 viathe user-input interface 860, or other appropriate mechanism. In anetworked environment, other software depicted relative to the computingsystem 810, or portions thereof, may be stored in the remote memorystorage device. By way of example, and not limitation, FIG. 8illustrates remote application programs 885 as residing on remotecomputing device 880. It will be appreciated that the networkconnections shown are exemplary and other means of establishing acommunications link between the computing devices may be used.

As discussed, the computing system may include a processor, a memory, abuilt in battery to power the computing device, an AC power input tocharge the battery, a display screen, a built-in Wi-Fi circuitry towirelessly communicate with a remote computing device connected tonetwork.

It should be noted that the present design can be carried out on acomputing system such as that described with respect to FIG. 8. However,the present design can be carried out on a server, a computing devicedevoted to message handling, or on a distributed system in whichdifferent portions of the present design are carried out on differentparts of the distributed computing system.

Another device that may be coupled to bus 811 is a power supply such asa battery and Alternating Current adapter circuit. As discussed above,the DC power supply may be a battery, a fuel cell, or similar DC powersource that needs to be recharged on a periodic basis. The wirelesscommunication module 872 may employ a Wireless Application Protocol toestablish a wireless communication channel. The wireless communicationmodule 872 may implement a wireless networking standard such asInstitute of Electrical and Electronics Engineers (IEEE) 802.11standard, IEEE std. 802.11-1999, published by IEEE in 1999.

Examples of mobile computing devices may be a wearable electronicdevice, a laptop computer, a cell phone, a personal digital assistant,or other similar device with on board processing power and wirelesscommunications ability that is powered by a Direct Current (DC) powersource that supplies DC voltage to the mobile device and that is solelywithin the mobile computing device and needs to be recharged on aperiodic basis, such as a fuel cell or a battery.

Network Environment

FIG. 7 illustrates diagrams of a network environment in which thetechniques described may be applied. The network environment 700 has acommunications network 220 that connects server computing systems 204Athrough 204C, and at least one or more client computing systems 202A to202F. As shown, there may be many server computing systems 204A through204C and many client computing systems 202A to 202F connected to eachother via the network 220, which may be, for example, the Internet.Note, that alternatively the network 220 might be or include one or moreof: an optical network, a cellular network, the Internet, a Local AreaNetwork (LAN), Wide Area Network (WAN), satellite link, fiber network,cable network, or a combination of these and/or others. It is to befurther appreciated that the use of the terms client computing systemand server computing system is for clarity in specifying who generallyinitiates a communication (the client computing system) and who responds(the server computing system). No hierarchy is implied unless explicitlystated. Both functions may be in a single communicating device, in whichcase the client-server and server-client relationship may be viewed aspeer-to-peer. Thus, if two systems such as the client computing system202A and the server computing system 204A can both initiate and respondto communications, their communication may be viewed as peer-to-peer.Likewise, communications between the server computing systems 204A and204-B, and the client computing systems 202A and 202C may be viewed aspeer-to-peer if each such communicating device is capable of initiationand response to communication. Additionally, server computing systems204A-204C also have circuitry and software to communication with eachother across the network 220. One or more of the server computingsystems 204A to 204C may be associated with a database such as, forexample, the databases 206A to 206C. Each server may have one or moreinstances of a virtual server running on that physical server andmultiple virtual instances may be implemented by the design. A firewallmay be established between a client computing system 202C and thenetwork 220 to protect data integrity on the client computing system202C. Each server computing system 204A-204C may have one or morefirewalls.

A cloud provider service can install and operate application software inthe cloud and users can access the software service from the clientdevices. Cloud users who have a site in the cloud may not solely managethe cloud infrastructure and platform where the application runs. Thus,the servers and databases may be shared hardware where the user is givena certain amount of dedicate use of these resources. The user'scloud-based site is given a virtual amount of dedicated space andbandwidth in the cloud. Cloud applications can be different from otherapplications in their scalability which can be achieved by cloning tasksonto multiple virtual machines at run-time to meet changing work demand.Load balancers distribute the work over the set of virtual machines.This process is transparent to the cloud user, who sees only a singleaccess point.

The cloud-based remote access is coded to utilize a protocol, such asHypertext Transfer Protocol (HTTP), to engage in a request and responsecycle with both a mobile device application resident on a client deviceas well as a web-browser application resident on the client device. Thecloud-based remote access for a wearable electronic device can beaccessed by a mobile device, a desktop, a tablet device, and othersimilar devices, anytime, anywhere. Thus, the cloud-based remote accessto a wearable electronic device hosted on a cloud-based provider site iscoded to engage in 1) the request and response cycle from all webbrowser based applications, 2) SMS/twitter based request and responsemessage exchanges, 3) the request and response cycle from a dedicatedon-line server, 4) the request and response cycle directly between anative mobile application resident on a client device and thecloud-based remote access to a wearable electronic device, and 5)combinations of these.

In an embodiment, the server computing system 204A may include a serverengine, a web page management component, a content management component,and a database management component. The server engine performs basicprocessing and operating system level tasks. The web page managementcomponent handles creation and display or routing of web pages orscreens associated with receiving and providing digital content anddigital advertisements. Users may access the server-computing device bymeans of a URL associated therewith. The content management componenthandles most of the functions in the embodiments described herein. Thedatabase management component includes storage and retrieval tasks withrespect to the database, queries to the database, and storage of data.

An embodiment of a server computing system to display information, suchas a web page, etc. is discussed. An application including any programmodules, apps, services, processes, and other similar softwareexecutable when executed on the server computing system 204A, causes theserver computing system 204A to display windows and user interfacescreens on a portion of a media space, such as a web page. A user via abrowser from the client computing system 202A may interact with the webpage, and then supply input to the query/fields and/or service presentedby a user interface of the application. The web page may be served by aweb server computing system 204A on any Hypertext Markup Language (HTML)or Wireless Access Protocol (WAP) enabled client computing system 202Aor any equivalent thereof. For example, the client mobile computingsystem 202A may be a wearable electronic device, smart phone, a touchpad, a laptop, a netbook, etc. The client computing system 202A may hosta browser to interact with the server computing system 204A. Eachapplication has a code scripted to perform the functions that thesoftware component is coded to carry out such as presenting fields andicons to take details of desired information. Algorithms, routines, andengines within the server computing system 204A take the informationfrom the presenting fields and icons and put that information into anappropriate storage medium such as a database. A comparison wizard isscripted to refer to a database and make use of such data. Theapplications may be hosted on the server computing system 204A andserved to the browser of the client computing system 202A. Theapplications then serve pages that allow entry of details and furtherpages that allow entry of more details.

Scripted Code

Any application and other scripted code components may be stored on anon-transitory computing machine-readable medium which, when executed onthe machine causes the machine to perform those functions. Theapplications including program modules may be implemented as logicalsequences of software code, hardware logic circuits, and any combinationof the two, and portions of the application scripted in software codeare stored in a non-transitory computing device readable medium in anexecutable format. In an embodiment, the hardware logic consists ofelectronic circuits that follow the rules of Boolean Logic, softwarethat contain patterns of instructions, or any combination of both.

The design is also described in the general context of computing deviceexecutable instructions, such as applications etc. being executed by acomputing device. Generally, programs include routines, objects,widgets, plug-ins, and other similar structures that perform particulartasks or implement particular abstract data types. Those skilled in theart can implement the description and/or figures herein ascomputer-executable instructions, which can be embodied on any form ofcomputing machine-readable media discussed herein.

Some portions of the detailed descriptions herein are presented in termsof algorithms/routines and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm/routine is here, andgenerally, conceived to be a self-consistent sequence of steps leadingto a desired result. The steps are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like. Thesealgorithms/routine of the application including the program modules maybe written in a number of different software programming languages suchas C, C++, Java, HTML, or other similar languages.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussions, itis appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computing system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computing system's registers andmemories into other data similarly represented as physical quantitieswithin the computing system memories or registers, or other suchinformation storage, transmission or display devices.

Although embodiments of this design have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of embodiments of this design as defined bythe appended claims. The invention is to be understood as not limited bythe specific embodiments described herein, but only by scope of theappended claims.

1. (canceled)
 2. A computer-implemented method, comprising: monitoringactivity data and a state of mind of an individual associated with anelectronic wearable device; determining a correlation between theactivity data and the state of mind of the individual; determining thatthe activity data and the state of mind of the individual, correspondingto the correlation, satisfy one or more notification criteria over apredetermined period of time; and generating at least one usernotification for presentation to the individual associated with thewearable electronic device.
 3. The computer-implemented method of claim2, further comprising: monitoring content from one or more timesynchronous applications of the wearable electronic device; and settingat least one goal associated with the one or more applications, based atleast in part on the content and the correlation between the activitydata and the state of mind of the individual.
 4. Thecomputer-implemented method of claim 3, further comprising: adding anevent to the one or more applications, the event associated with the atleast one goal when the at least one goal is not achieved within apredetermined period of time.
 5. The computer-implemented method ofclaim 3, wherein at least one of the one or more applications logsinformation in a time-based format, the information including at leastone of: personal communication data, information from a timelineapplication, or information from a calendar application; and thepersonal communication data comprises at least one of: email data,social media data, or text message (SMS) data.
 6. Thecomputer-implemented method of claim 3, further comprising: comparing,by an insight engine, the content against at least one historicalaverage of the content; and cross-referencing the one or moreapplications to determine whether to transmit the at least one usernotification for presentation to the individual associated with thewearable electronic device.
 7. The computer-implemented method of claim3, wherein monitoring content from the state of mind further comprisesconfiguring an interface to convey questions to the individual about amood of the individual and receiving replies thereto.
 8. Thecomputer-implemented method of claim 7, further comprising correlatinginformation associated with the mood of the individual with the activitydata and cross referencing the correlated information with one or moreevents logged in the one or more time synchronous applications togenerate the at least one user notification.
 9. A computing system,comprising: at least one processor; and memory including instructionsthat, when executed by the at least one processor, cause the computingsystem to: monitor activity data and a state of mind of an individualassociated with a wearable electronic device; determine a correlationbetween the activity data and the state of mind of the individualassociated with the wearable electronic device; determine that theactivity data and the state of mind of the individual, corresponding tothe correlation, satisfy one or more notification criteria over apredetermined period of time; and generate at least one usernotification for presentation to the individual associated with thewearable electronic device.
 10. The computing system of claim 9, whereinthe instructions when executed further cause the computing system to:monitor content from one or more applications of the wearable electronicdevice; and set at least one goal associated with the one or moreapplications, based at least in part on the content and the correlationbetween the activity data and the state of mind of the individual. 11.The computing system of claim 10, wherein the instructions when executedfurther cause the computing system to: add an event to the one or moreapplications, the event associated with the at least one goal when theat least one goal is not achieved within a predetermined period of time.12. The computing system of claim 9, wherein at least one of the one ormore applications logs information in a time-based format, theinformation including at least one of: personal communication data,information from a timeline application, or information from a calendarapplication; and the personal communication data comprises at least oneof: email data, social media data, or text message (SMS) data.
 13. Thecomputing system of claim 10, wherein the instructions when executedfurther cause the computing system to: compare, by an insight engine,the content against the at least one historical average of the content;and cross-reference the one or more applications to determine whether totransmit the at least one user notification to the wearable electronicdevice.
 14. The computing system of claim 10, wherein monitoring contentfrom the state of mind further comprises configuring an interface toconvey questions to the individual about a mood of the individual andreceiving replies thereto.
 15. The computing system of claim 14, whereinthe instructions when executed further cause the computing system to:correlate information associated with the mood of the individual withthe activity data and cross referencing the correlated information withone or more events logged in the one or more applications to generatethe at least one notification.
 16. A non-transitory computer-readablestorage medium including instructions that, when executed by one or moreprocessors, cause the one or more processors to: monitor activity dataand a state of mind of an individual associated with a wearableelectronic device; determine a correlation between the activity data andthe state of mind of the individual associated with the wearableelectronic device; determine that the activity data and the state ofmind of the individual, corresponding to the correlation, satisfy one ormore notification criteria over a predetermined period of time; andgenerate and communicate at least one user notification to a display ofthe wearable electronic device.
 17. The non-transitory computer-readablestorage medium of claim 16, wherein the instructions when executedfurther cause the one or more processors to: monitor content from one ormore time applications of the wearable electronic device; and set atleast one goal associated with the one or more applications, based atleast in part on the content and the correlation.
 18. The non-transitorycomputer-readable storage medium of claim 17, wherein the instructionswhen executed further cause the one or more processors to: adding anevent to the one or more applications, the event associated with the atleast one goal when the at least one goal is not achieved within apredetermined period of time.
 19. The non-transitory computer-readablestorage medium of claim 17, wherein at least one of the one or moreapplications logs information in a time-based format, the informationincluding at least one of: personal communication data, information froma timeline application, or information from a calendar application,wherein the personal communication data comprises at least one of: emaildata, social media data, or text message (SMS) data.
 20. Thenon-transitory computer-readable storage medium of claim 17, wherein theinstructions when executed further cause the one or more processors to:compare, by an insight engine, the content against the at least onehistorical average of the content; and cross-reference the one or moreapplications to determine whether to transmit the at least one usernotification to the wearable electronic device.
 21. The non-transitorycomputer-readable storage medium of claim 16, wherein monitoring contentfrom the state of mind further comprises configuring an interface toconvey questions to the individual about a mood of the individual andreceiving replies thereto.